Task: Develop SW integration verification plan
Development of the SW verification plan for a specific level of the software hierarchy, describing the verification tools, methods and environment with pass and fail criteria.
Purpose
To develop of  the SW verification plan for a specific level of the software hierarchy,
Relationships
Main Description

ISO 26262, vol 8, clause 9 defines the guidance for generic aspects of verification planning which should be followed. in terms of the definitions in this clause the software integration test objects are the software components (i.e. collections of software units).

For model based development the software integration can be replaced with integration at the model level with subsequent automatic code generation for the integration model.

The intent is that the software integration tests shall demonstrate that the software components and embedded software should be robust with enough resources to support the functionality and achieve compliance with the software architectural design, and the hardware software interface. The tests should also verify that the software has the correct implementation of the intended functionality.

This task has been broken down into three steps indicated below, these cover

The Determination of the methods for software integration testing

The Determination of the methods for deriving test cases for SW integration testing

The Determination of the structural coverage metrics at the SW architectural level




Steps
Determine the methods for software integration testing

The table below from ISO 26262, vol 6, clause 10.4.3 indicates the applicable methods for determining the software integration tests

Methods for software integration testing 

This table/figure is taken from ISO 26262:2011-10.4.3 © ISO 2011 – All rights reserved. Reproduced with the permission of ANSI on behalf of ISO.

The objective of these tests is to be able demonstrate that both the SW components and the embedded architecture achieve compliance with

The SW architectural design

The HW-SW interfaces

The specified functionality

Robustness

And sufficient resources to support the functionality

Copyright ISO 2011. All rights reserved. Reproduced with permission of ANSI.  

Determine the methods for deriving test cases for SW integration testing

To enable the specification of appropriate test cases for the software integration test methods selected in the previous step, test cases shall be derived from the table below from ISO 26262, vol 6, clause 10.4.4

Methods for deriving test cases for software integration testing 

This table/figure is taken from ISO 26262:2011-10.4.4 © ISO 2011 – All rights reserved. Reproduced with the permission of ANSI on behalf of ISO.

To evaluate the completeness of tests and to obtain confidence that there is no unintended functionality, the coverage of requirements at the software architectural level by test cases shall be determined. If necessary, additional test cases shall be specified or a rationale shall be provided.

Copyright ISO 2011. All rights reserved. Reproduced with permission of ANSI.  

Determine the structural coverage metrics at the SW archtiectural level

The determination of the structural coverage metrics is required for items of ASIL C or D and recommended to items of ASIL A or B. The objective of this step is to evaluate the completeness of test cases and to obtain confidence that there is no unintended functionality, the structural coverage shall be measured in accordance with the metrics listed in the table below from ISO 26262 vol 6, clause 10.4.6

Structural coverage metrics at the software architectural level 

This table/figure is taken from ISO 26262:2011-10.4.6 © ISO 2011 – All rights reserved. Reproduced with the permission of ANSI on behalf of ISO.

If the achieved structural coverage is considered insufficient, either additional test cases shall be specified or a rationale shall be made available.

Appropriate software tools can be used to determine the structural coverage.

Copyright ISO 2011. All rights reserved. Reproduced with permission of ANSI.  

Key Considerations

Practices applicable to help develop the SW integration verification plan are

It should be noted that only some of the tasks in these practices are directly relevant to the planning stage, but part of that planning is to understand what is involved in this testing so the Back to Back, Model and Requirements based testing are included in this section to help the users understand the processes required for these methods.
More Information